Dynamically binding data in an application

ABSTRACT

A method for binding data in an application. An expression is created via a framework based on input from a developer. The expression is received at an expression engine wherein the expression describes a relation between a first property of a first data of the application to a first property of a second data of the application. A binding is created between the first data and the second data based on the relation via the expression engine. The first property of the second data is changed based on a change to the first property of the first data wherein the changing occurs because of the binding. The receiving the expression, the creating the binding, and the changing the first property are orchestrated via the framework to manage when the expression is executed in the application.

RELATED APPLICATION

This application claims priority to and benefit of the U.S. ProvisionalPatent Application 61/529,178, entitled “LIVE BINDINGS” with the filingdate of Aug. 30, 2011, by John Thomas et al., assigned to the assigneeof the present application, and which is herein incorporated byreference in its entirety.

This application additionally claims priority to and benefit of the U.S.Provisional Patent Application 61/529,192, entitled “RUN TIME TYPEINFORMATION” with the filing date of Aug. 30, 2011, by John Thomas etal., assigned to the assignee of the present application, and which isherein incorporated by reference in its entirety.

FIELD OF THE TECHNOLOGY

The present technology relates generally to dynamically binding data inan application.

BACKGROUND

A variety of modern electronic devices have the ability to executesoftware applications. Software applications may be designed for avariety of functions or purposes but most, if not all softwareapplications, require the manipulation of data. Data manipulation mayrequire a developer to write a great deal of code in an application todirect and control the manipulation of data. Such code generation istime consuming and takes the developer's focus off of the actualfunction and purpose of the software application.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of an environment for binding data in anapplication in accordance with embodiments of the present technology.

FIG. 2 is a block diagram of an environment for binding data in anapplication in accordance with embodiments of the present technology.

FIG. 3 illustrates a flowchart of an example method for binding data inan application, in accordance with embodiments of the presenttechnology.

FIG. 4 illustrates a flowchart of an example method for binding data inan application, in accordance with embodiments of the presenttechnology.

The drawings referred to in this description of embodiments should beunderstood as not being drawn to scale except if specifically noted.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments of the presenttechnology, examples of which are illustrated in the accompanyingdrawings. While the technology will be described in conjunction withvarious embodiment(s), it will be understood that they are not intendedto limit the present technology to these embodiments. On the contrary,the present technology is intended to cover alternatives, modificationsand equivalents, which may be included within the spirit and scope ofthe various embodiments as defined by the appended claims.

Furthermore, in the following description of embodiments, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present technology. However, the present technologymay be practiced without these specific details. In other instances,well known methods, procedures, user interface controls, and circuitshave not been described in detail as not to unnecessarily obscureaspects of the present embodiments.

Unless specifically stated otherwise as apparent from the followingdiscussions, it is appreciated that throughout the present descriptionof embodiments, discussions utilizing terms such as “receiving,”“creating,” “moving,” “modifying,” “altering,” “querying,” or the like,refer to the actions and processes of a computer system, or similarelectronic computing device. The computer system or similar electroniccomputing device, such as a smart phone, or handheld mobile device,manipulates and transforms data represented as physical (electronic)quantities within the computer system's registers and memories intoother data similarly represented as physical quantities within thecomputer system memories or registers or other such information storage,transmission, or display devices. Embodiments of the present technologyare also well suited to the use of other computer systems such as, forexample, optical and mechanical computers.

Overview of Dynamically Binding Data in an Application

Embodiments of the present technology are for binding data in anapplication. Software applications or software programs require themanipulation and movement of data, objects and other information. Asoftware application may have more than one layer such as a presentationlayer that the user experiences and the database layer that stores datathat may or may not be accessed in the execution of the of theapplication. The presentation layer may comprise control objects whilethe database layer comprises source objects. There exists a need whendeveloping and executing an application to bind a control object to asource object such that the source object may be moved from the databaselayer of the application to the presentation layer of the application asneeded. The source object may or may not be modified and then moved backto the database layer. Such movement of data or objects may be referredto as data binding. A developer may be required to manually create suchbinding or rely on a compiler to create the bindings based on code. Thepresent technology operates to create such bindings in an efficient andautomated manner.

An expression engine may be employed at a computer system to create thebindings between objects. The bindings may be created automatically anddynamically during the execution of the application or may be createdduring the development of the application. The expression engine is ableto receive an expression which relates or requires a relation betweentwo objects. The expression may be a command from a developer or user ofthe application and may be written in a programming language or may bewritten in a more general expressive language or may be created in auser interface with inputs from a keyboard, mouse or the like. Theexpression engine then creates the binding by evaluating the requiredrelation and the properties associated with the object that are of thetype necessary for the required relation. For example, the object maycomprise data related to customer name and the required relationnecessitates the data of the customer name. The expression engine thencreates a binding linking the control object, which performs thefunction required by the application, and the source object whichcomprises the data of the customer name. During execution of theapplication the source object may be modified. For example, the customername may be changed in the source object; the source object may then bemoved back to the database layer of the application with themodifications.

In one embodiment, the expression engine does not know the data type ofa given object, therefore this knowledge must be discovered by theexpression engine. The expression engine may employ run time typeinformation (RTTI) to query the object to gain information regarding theobject's data type and data types of its properties. Thus RTTI is amechanism that may be employed by the expression engine or developer toquery objects regarding their data and capabilities. This informationmay then be used to make dynamic bindings between objects.

RTTI is a way of introspection. For example, RTTI may be employed todiscover the text property of a source object. To create a binding thatwill allow edit control of this text property, the expression enginemust first discover the text control. RTTI is used to discover the textproperty of a control and its data type, such as a string, and then theexpression engine binds a control object's text property that is able toread and edit the text property of the source object. A binding may binda number to a string or any data type to another data type. Thus, thepresent technology operates to bind two string objects together throughthe text properties.

The present technology provides for many examples of binding data in anapplication. The following discussion will demonstrate various hardware,software, and firmware for binding data in an application in variousembodiments of the present technology. Furthermore, the systems andmethods may include some, all, or none of the hardware, software andfirmware discussed below.

Dynamically Binding Data in an Application

Referring to the figures, exemplary embodiments of the technology willnow be described. The following description will focus on embodiments ofthe present technology, which are systems and methods for binding datain an application. The present technology, however, is not limited toany one particular device, operating system, environment, or platform.Instead, those skilled in the art will find that the system and methodsof the present technology may be advantageously embodied on a variety ofdifferent platforms. Therefore, the description of the exemplaryembodiments that follows is for purposes of illustration and notlimitation.

FIG. 1 is a block diagram illustrating environment 100 which is anexample environment comprising computer system 105, first data 110,property 111, presentation layer 115, binding 112, second data 120,property 121, application layer 122, third data 124, property 126,database layer 125, application 130, interface 135, component 140,expression 150, expression engine 155, and framework 160. Environment100 depicts computer system 105 as a hardware device for carrying outthe present technology. Computer system 105 may be a general purposecomputer system, an embedded computer system, a personal computer suchas a desktop computer, a laptop, a notebook, an electronic handhelddevice, a personal digital assistant, a smart phone, a tablet computer,a net book, user devices, or the like. In one embodiment, computersystem 105 comprises memory, storage and a processor such as a centralprocessing unit that carry out the instructions of a computer programsuch as an operating system or portions of the present technology.Computer system 105 may also comprise a graphics processing unit (GPU)to process and render display features. In one embodiment, the presenttechnology is part of LiveBindings software products developed byEmbarcadero Technologies.

Application 130 is a software program, a software application, or appdesigned to execute or run on a hardware system such as computer system105. In one embodiment, application 130 is in the processes of beingdesigned by a developer on computer system 105. In one embodiment,application 130 is in the process of being executed on computer system105 operating as an end user device. Application 130 comprisespresentation layer 115 which is a layer, a portion or a part ofapplication 130 designed for interaction with an end user. Presentationlayer 115 comprises first data 110 which may be data, information, or anobject associate with application 130. In one embodiment, first data 110is a control object which is a component or part of application 130designed to control data in application 130. Application 130 alsocomprises database layer 125 which is a layer, portion, or part ofapplication 130 that is a database or storage location for data,information and objects such as second data 120. In one embodiment,second data 120 is a source object which comprises data and otherfunctions or capabilities. For example, a source object may comprisetext fields that house information such as names, customer names, creditcard information, inventory, etc. A source object may also havefunctions such as the ability to be modified. Binding 112 depicts abinding or link between first data 110 and second data 120.

Application 130 may include framework 160. Framework 160 is for creatingan expression or a plurality of expressions used to create bindings suchas binding 112. For example, framework 160 is able to receive input froma developer or other user regarding the intent of the developer. Theinput may be received in the form of code, plain language, or otherinput. Framework 160 then generates or creates the expression based onthe intent of the developer. Framework 160 is also capable oforchestrating or managing the movement of data and objects through theapplication and layers such as the movement of second data 120 throughpresentation layer 115 and database layer 125. This orchestration ormanagement may include managing the creation of expressions, thecreation of bindings, and changes or modifications to data or objects.Framework 160 may also have control over expression engine 155. In oneembodiment, framework 160 is employed to decide when to execute anexpression in application 130. For example, the intent of the user mayrequire an expression to be executed only when a user of application 130issues a command via the controls of application 130.

In one embodiment, application 130 comprises application layer 122 whichmay be described as an application logic layer and in general comprisesdata, information, and objects running, executing, or contained byapplication 130 such as third data 124. Presentation layer 115, databaselayer 125 and application layer 122 may be described as a softwarestack. It should be appreciated that first data 110, second data 120,and third data 124 may be contained by presentation layer 115, databaselayer 125 and application layer 122. The data may be bound to anotherdata within the same layer or a different layer and a data may be movedbetween layers while maintaining a binding with another data. Binding112 is depicted as linking first data 110 and second data 120. Binding112 may link first data 110 to third data 124 or second data 120 tothird data 124. In one embodiment, binding 112 may link a data toitself.

First data 110, second data 120, and third data 124 may each compriseproperty 111, property 121 and property 126 respectively. Property 111,property 121 and property 126 are properties or data properties of acomponent. A property has a data type associated with it. For example, adata may comprise information, the type of property of the data is textand the property is the actual text associated with the data. Thepresent technology dynamically creates bindings between objects or dataand may do so based on the property of the data. For example, binding112 may bind property 111 and property 121 together such that ifproperty 111 is changed, then the expression engine will change property121 based on the change to property 111 wherein the change occursbecause of binding 112. Thus first data 110 and second data 120 arebound together. A data or object may have more than one property and/orproperty type and a data or object may be linked to another object withmore than binding associated with one or more properties of the object.An object may also be subject to multiple bindings with multipleobjects. In one embodiment, a first property of an object is bound to asecond property of the same object.

It should be appreciated that a property in the source could bedifferent from the property in the control and vice versa. The bindingmay operate to bind a number to a string or any other data type. Such abinding may convert the data type as it moves through the layers of theapplication. For example, a data or object may be a calendar or data fora calendar. The calendar data may be stored as a number when it is inthe database layer, but it needs to be converted to a string in thepresentation layer. The binding operates such that the data type isconverted appropriately as the data moves from one layer to another.Such conversions may be controlled by the expression engine or theframework.

In one embodiment, computer system 105 comprises expression engine 155.It should be appreciated that expression engine 155 may be a componentor part of application 130 and may also be a component or part of anapplication used for designing application 130. Expression engine 155 isfor receiving an expression such as expression 150. Expression 150 maybe generated by a developer of application 130, a user of application130, by application 130, or by expression engine 155. Expression 150 maydefine or require a relationship between two objects or two pieces ofdata. For example, expression 150 may describe that the name of acustomer is to be entered into a data field of second data 120 as thename is received as data from a user in presentation layer 115. Firstdata 110 may be a control object that can control or edit such data.Expression engine 155 then binds first data 110 to second data 120 suchthat first data 110 can control second data 120, a source object, toenter or modify the customer name in second data 120 as data is receivedfrom a user of application 130. The source object may have propertiesassociated with it and the source object may be assigned a valueaccording to a local variable in the control object. In one embodiment,expression engine 155 operates with a compiler to create the bindings.The expression engine 155 allows a developer to create application 130with these described bindings without having to write code directed toeach of the bindings as expression engine 155 allows for the process tobe automated.

Expression 150 may be generated using a programming language such as C++or Delphi or other well-known languages. Expression 150 may also begenerated using more general or plain language expressions or may begenerated in a user interface used to graphically design application130. The present technology is based on relational expressions calledbinding expressions that can be either unidirectional or bidirectional.The present technology is also about control objects and source objects.By means of these binding expressions, any source object can be bound toitself, it becomes both source and control object, or to any othercontrol object, simply by defining a binding expression involving one ormore properties of the objects you want to bind together. For example,you can bind an edit control to a label so that, when the text changesin the edit box, the caption of the label is automatically adjusted tothe value evaluated by your binding expression.

In the general execution of application 130, presentation layer 115 mayuse first data 110 to control second data 120 and move second data 120from database layer 125 to presentation layer 115. At this point a usermay enter data to modify or alter second data 120. After which seconddata 120 may be moved back to database layer 125. For this to beaccomplished, first data 110 must first be linked or bound to seconddata 120 so that first data 110 knows where to find second data 120 andhow to carry out operations regarding second data 120. Expression engine155 solves this problem by creating binding 112 to bind first data 110to second data 120. This may be accomplished by expression engine 155evaluating first data 110 and second data 120 to understand theirrespective data types, functions and capabilities. In one embodiment,expression engine 155 has no prior knowledge of first data 110 andsecond data 120. Application 130 may not be able to provide suchknowledge to expression engine 155, therefore expression engine 155 mustdiscover this knowledge itself. In one embodiment, this knowledge isdiscovered using run time type information (RTTI).

In one embodiment, bindings may be employed to propagate a change to aplurality of objects or data that are connected via a chain of bindings.For example, first data 110 may be bound to second data 120 and seconddata 120 may be bound to a third data such that when a property ofsecond data 120 is changed due to the binding, the change is propagatedto the appropriate property of the third data through the bindingbetween second data 120 and the third data. In one embodiment,expression engine 155 is employed to create and manage a plurality ofbindings associated with a plurality of objects or data. Additionally,bindings may be grouped together in a binding list which is a collectionof bindings created for application 130. The binding or binding listsmay be presented to a developer graphically in interface 135 where thedeveloper may view, change, remove, modify or alter the bindings and itsparameters and properties.

A solution for binding data is to use a database editor such as DBEditworking with a TField. In such a solution, the DBEdit may be able toextract data out of the TField and send it back in the other direction.However, if another editor or control is desired in conjunction withDBEdit, then additional effort is required by the developer. The presenttechnology does not require the use of DBEdit or other database editorssuch as TEdit and instead uses an intermediary set between the edit andthe field to manage moving data between layers of application 130. Theuse of RTTI allows the expression engine 155 to create a binding anddoes not have to consider the type of database editor required to editthe source object. The RTTI allows the expression engine to simply haveknowledge of the data type of the source object and then expressionengine 155 creates the binding accordingly. For example, RTTI may beable to identify that the source object has text which is all theknowledge that expression engine 155 may be required to have in a givenembodiment.

In one embodiment, computer system 105 comprises interface 135 andcomponent 140. Interface 135 may be a graphical user interface employedby a developer to develop application 130 by clicking and draggingvisual or graphical components into desired locations. Application 130may be located within interface 135 during the development ofapplication 130. Interface 135 may include libraries of predefinedvisual objects, buttons, text fields, etc. employed in the design of anapplication. Component 140 may be a visual component such as a buttonthat is placed within application 130 by the developer. The graphicaluser interface may be part of a larger platform used to design ordevelop applications. For example, a component may be a button to beused in a menu associated with the application. The platform andinterface may provide an application developer with a plurality ofstandard buttons to choose. The application developer makes a selectionby clicking and dragging the desired button into position within theinterface. The button, or other component, may also comprise a varietyof properties such as color, animations, effects, style, text, font,text size, etc. In one embodiment, the interface 135 is part ofFiremonkey software products developed by Embarcadero Technologies usedfor creating and executing applications.

FIG. 2 is a block diagram illustrating environment 200 which is anexample environment comprising expression engine 205, managed binding210, unmanaged binding 215, RTTI 220, dependency 225, scope 230,expression evaluator 235, and expression parser 240. It should beappreciated that expression engine 205, in embodiments, has the samefeatures, capabilities and functions of expression engine 155 of FIG. 1.

Expression engine 205 may comprise both managed binding 210 andunmanaged binding 215. In one embodiment, managed binding 210 is amanaged binding in which expression engine 205 is employed to direct thedata in a predetermined fashion by executing an expression. In oneembodiment, managed binding 210 comprises multiple points of data thatare all connected by an edit control and connected to a slider such thatif a value is changed in the edit control, it changes or slides thevalue of all the data connected to the edit control. This may allow anexpression to be reevaluated automatically. Unmanaged binding 215 is abinding that is not managed in a predetermined fashion and may be acollection of data. In one embodiment, two data points are connected toone another by a binding and if one is changed, the other is changedbased on a dependency created by the binding.

RTTI 220 comprises run time type information that is available to aprogramming language and is employed by expression engine 205 in thesame manner in which expression engine 155 of FIG. 1 employs RTTI. Inone embodiment, RTTI 220 has more introspection than the basic nativetypes that C programmers and C++ programmers use. The introspection thatwas added in the present technology comprises line type information forboth the classes and methods to describe the layout of the classes andthe basic method types. Thus, the present technology allows a developerto query the run-type information for the object, and know a lot moreabout it. RTTI 220 also allows a developer to invoke procedures so, ifthe developer wants to call a method on an object, the developer now hasenough information to take the pointer to the object and point to themethod and invoke the method with the appropriate parameters. RTTI 220comprises detailed information about all the parameter types for theprocedures and what those actual types are. Those types can be all kindsof different types and they can be pointing to other classes that haverun time type information. RTTI 220 provides detailed segmentinformation for all the structures in a simple pellet structure with 30fields that are laid out for the types, for all the fields.

RTTI may be described as a programming paradigm in which informationabout a type can be obtained at run time with no prior knowledge of thetype. If RTTI generation is enabled, the resulting binary includesspecial metadata that contains information about types (for example,class ancestry, declared fields, annotated attributes). Using thefunctionality provided in the RTTI unit, you can obtain this informationat run time. The net result is the ability to create more abstract andgeneralized frameworks that can operate on any type that exposes RTTI.RTTI information is stored in the compiled binary, which means it doesnot need actual initialization. RTTI builds up a clean, object-orientedinterface that can be easily used in any application. The RTTI unitprovides a special record, called TRTTIContext which manages thelifetime of all objects created during an RTTI work session.

Dependency 225 may be a component of expression engine 205 and maycomprise the ability to manage dependency for data or objects and howthey are bound to one another. Thus if an object is dependent uponanother object, if the other object is changed then dependency 225changes the first object accordingly. In one embodiment, expressionengine 205 comprises scope 230. Scope 230 allows the scope of an objectto be defined by a developer. In one embodiment, the scope of the objectand its binding may include two expressions. For example, the R valueand the L value where the L value is value assigned to a binding and theR value produces a value and may use operators or methods. Expressionevaluator 235, in one embodiment, is employed to evaluate an expressionsuch as expression 150 of FIG. 1 to determine what operations must becarried out and what bindings must be formed to satisfy the expression.Expression parser 240 then operates to parse the expression.

Operations

FIG. 3 is a flowchart illustrating process 300 for binding data in anapplication, in accordance with one embodiment of the present invention.In one embodiment, process 300 is carried out, at least in part, byprocessors and electrical user interface controls under the control ofcomputer readable and computer executable instructions stored on acomputer-usable storage medium. The computer readable and computerexecutable instructions reside, for example, in data storage featuressuch as computer usable volatile and non-volatile memory and arenon-transitory. However, the non-transitory computer readable andcomputer executable instructions may reside in any type ofcomputer-usable storage medium. In one embodiment, process 300 isperformed by the devices and components in FIGS. 1 and 2.

At 301, an expression is created via a framework based on input from adeveloper. For example, framework 160 of FIG. 1 may be used.

At 302, the expression is received at an expression engine wherein theexpression describes a relation between a first data associated with apresentation layer of the application to a second data associated with adatabase layer of the application. In one embodiment, the expression isexpression 150, the first data is first data 110, the second data issecond data 120, and the expression engine is expression engine 155 ofFIG. 1. In one embodiment, the first and second data are objects in asoftware application such as control objects or source objects. 302 mayoccur during the development of the application or may occur during theexecution of the application.

At 304, a binding is created between the first data and the second databased on the relation via the expression engine. In one embodiment, thebinding is binding 112 of FIG. 1. The binding may be created via theexpression engine employing RTTI to query the first and second data todiscover knowledge such as the data types of the first and second data.304 may occur during the development of the application or may occurduring the execution of the application. It should be appreciated thatthe development of the application may occur via code written in aprogramming language and compiled into an application or may occur via avisual program for designing application in a graphical user interface.In one embodiment, the application is developed using C++ programminglanguage. The binding may allow the first and/or second data to move inunidirectional or bidirectional manners. In one embodiment, 302 and 304are repeated for a plurality of bindings created for a plurality ofobjects.

At 305, the first property of the second data is changed based on achange to the first property of the first data wherein the changingoccurs because of the binding.

At 306, the receiving the expression, the creating the binding, and thechanging the first property are orchestrated via the framework to managewhen the expression is executed in the application.

At 307, the second data is moved from the database layer of theapplication to the presentation layer of the application based on thebinding during an execution of the application.

At 308, the second data is modified in the presentation layer of theapplication based on information received from a user. For example, thesecond data may comprise a text field that is changed due to user input.

At 310, the second data is moved from the presentation layer of theapplication back to the database layer of the application after themodifying the second data. Thus the second data may be described as anobject that may be moved in a bidirectional fashion due to its binding.

At 316, a property of the second data is altered based on the binding.For example, a text field of the second data may be altered.

At 318, a property of a third data bound to the second data is alteredbased on the altering the property of the second data. The third datamay comprise a text field that correlates to the text field associatedwith the second data and thus the binding between the second and thirddata propagates the change to the third data.

FIG. 4 is a flowchart illustrating process 400 for binding data in anapplication, in accordance with one embodiment of the present invention.In one embodiment, process 400 is carried out, at least in part, byprocessors and electrical user interface controls under the control ofcomputer readable and computer executable instructions stored on acomputer-usable storage medium. The computer readable and computerexecutable instructions reside, for example, in data storage featuressuch as computer usable volatile and non-volatile memory and arenon-transitory. However, the non-transitory computer readable andcomputer executable instructions may reside in any type ofcomputer-usable storage medium. In one embodiment, process 400 isperformed by the devices and components in FIGS. 1 and 2. In oneembodiment, the application is developed using C++ programming language.

At 401, an expression is created via a framework based on input from adeveloper. For example, framework 160 of FIG. 1 may be used.

At 402, an expression is received at an expression engine wherein theexpression describes a relation between a first data associated with apresentation layer of the application to a second data associated with adatabase layer of the application.

At 404, the first data and the second data are queried for run time typeinformation (RTTI) via the expression engine.

At 406, a binding is created between the first data and the second databased on the relation and the RTTI via the expression engine.

At 407, the first property of the second data is changed based on achange to the first property of the first data wherein the changingoccurs because of the binding.

At 408, the receiving the expression, the creating the binding, and thechanging the first property are orchestrated via the framework to managewhen the expression is executed in the application.

At 410, the second data is moved from the database layer of theapplication to the presentation layer of the application based on thebinding during an execution of the application.

While the technology is described in some detail with specific referenceto embodiments and alternatives, there is no intent to limit thetechnology to a particular embodiment or specific alternatives. Forinstance, those skilled in the art will appreciate that modificationsmay be made to embodiments without departing from the teachings of thepresent technology.

Example Computer System Environment

The present technology may be carried out, associated with or otherwisepracticed with a computer system. Portions of the present technology arecomposed of computer-readable and computer-executable instructions thatreside, for example, in computer-usable media of a computer system orother user device such as computer system 105 of FIG. 1. Described belowis an example computer system or components that may be used for or inconjunction with aspects of the present technology such for binding datain an application.

It is appreciated that that the present technology can operate on orwithin a number of different computer systems including general purposenetworked computer systems, embedded computer systems, a personalcomputer such as a desktop computer, a laptop, a notebook, an electronichandheld device, a personal digital assistant, a smart phone, a tabletcomputer, a net book, user devices, and the like. The computer system iswell adapted to having peripheral computer readable media such as, forexample, a floppy disk, a compact disc, flash memory and the likecoupled thereto.

The computer system includes an address/data bus for communicatinginformation, and a processor coupled to bus for processing informationand instructions. The computer system is also well suited to amulti-processor or single processor environment and also includes datastorage features such as a computer usable volatile memory, e.g. randomaccess memory (RAM), coupled to bus for storing information andinstructions for processor(s).

The computer system may also include computer usable non-volatilememory, e.g. read only memory (ROM), as well as input devices such as analpha-numeric input device, a mouse, or other commonly used inputdevices. The computer system may also include a display such as liquidcrystal device, cathode ray tube, plasma display, and other outputcomponents such as a printer or other common output devices.

The computer system may also include one or more signal generating andreceiving device(s) coupled with a bus for enabling the system tointerface with other electronic devices and computer systems. Signalgenerating and receiving device(s) of the present embodiment may includewired serial adaptors, modems, and network adaptors, wireless modems,and wireless network adaptors, and other such communication technology.The signal generating and receiving device(s) may work in conjunctionwith one or more communication interface(s) for coupling information toand/or from the computer system. A communication interface may include aserial port, parallel port, Universal Serial Bus (USB), Ethernet port,antenna, or other input/output interface. A communication interface mayphysically, electrically, optically, or wirelessly (e.g. via radiofrequency) couple the computer system with another device, such as acellular telephone, radio, a handheld device, a smart phone, or computersystem.

Although the subject matter is described in a language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed:
 1. A non-transitory computer readable medium havinginstructions embodied therein that when executed cause a computer systemto perform a method for dynamically binding data in an application, saidmethod comprising: creating an expression via a framework based on inputfrom a developer; receiving said expression at an expression enginewherein said expression describes a relation between a first property ofa first data of said application to a first property of a second data ofsaid application, wherein said first data is associated with apresentation layer of said application and wherein said second data isassociated with a database layer of said application; creating a bindingbetween said first data and said second data based on said relation viasaid expression engine; changing said first property of said second databased on a change to said first property of said first data wherein saidchanging occurs because of said binding; orchestrating said receivingsaid expression, said creating said binding, and said changing saidfirst property via said framework to manage when said expression isexecuted in said application; moving said second data from said databaselayer of said application to said presentation layer of said applicationbased on said binding during an execution of said application; modifyingsaid second data in said presentation layer of said application based oninformation received from a user; and moving said second data from saidpresentation layer of said application back to said database layer ofsaid application after said modifying said second data.
 2. Thenon-transitory computer readable medium of claim 1 wherein saidreceiving said expression and said creating said binding areaccomplished using run time type information (RTTI) associated with saidfirst data and said second data.
 3. The non-transitory computer readablemedium of claim 1 wherein said receiving said expression and saidcreating said binding occur during development of said application. 4.The non-transitory computer readable medium of claim 3 wherein saiddevelopment of said application occurs via a manipulation of visualcomponents associated with a graphical user interface.
 5. Thenon-transitory computer readable medium of claim 1 wherein saidreceiving said expression and said creating said binding occurdynamically during an execution of said application.
 6. Thenon-transitory computer readable medium of claim 1 wherein said bindingoccurs to allow said first data or said second data to moveunidirectional.
 7. The non-transitory computer readable medium of claim1 wherein said binding occurs to allow said first data or said seconddata to move bidirectional.
 8. The non-transitory computer readablemedium of claim 1 wherein said first data is a control object of saidapplication and said second data is a source object of said application.9. The non-transitory computer readable medium of claim 1 wherein saidchanging said first property of said second data converts a data type ofsaid second data to a new data type.
 10. The non-transitory computerreadable medium of claim 1 wherein said receiving said expression, saidcreating said binding and said moving said second data are repeated tocreate a plurality of bindings based on a plurality of expressions. 11.The non-transitory computer readable medium of claim 1, furthercomprising: altering a property of said second data based on saidbinding; and altering a property of a third data bound to said seconddata based on said altering said property of said second data.
 12. Thenon-transitory computer readable medium of claim 1 wherein saidapplication was developed using C++ programming language.
 13. Thenon-transitory computer readable medium of claim 1 wherein said creatingsaid expression creates a plurality of expressions and said creatingsaid binding creates a plurality of bindings based on said plurality ofsaid expressions.
 14. A non-transitory computer readable medium havingcomputer readable program code embedded therein that when executedcauses a computing system to dynamically bind data in an application,said program code comprising: a first data with a first property,wherein said first data is associated with a presentation layer of saidapplication; a second data with a first property, wherein said seconddata is associated with a database layer of said application; anexpression relating said first data to said second data; and anexpression engine for querying said first data and said second data forrun time type information (RTTI), receiving said expression, bindingsaid first data to said second data based on said RTTI and saidexpression and for changing said first property of said second databased on a change to said first property of said first data wherein saidchanging occurs because of said binding, wherein said expression engineis for moving said second data from said database layer of saidapplication to said presentation layer of said application based on saidbinding during an execution of said application; and a framework forcreating said expression based on input from a developer and fororchestrating a movement of said first data and said second data in saidapplication to control when said expression is executed in saidapplication.
 15. The non-transitory computer readable medium of claim 14wherein said application was developed using C++ programming language.16. The non-transitory computer readable medium of claim 14, furthercomprising: a graphical user interface at said computing system formanipulating said expression and properties of said first data and saidsecond data.
 17. The non-transitory computer readable medium of claim 14wherein said binding is a managed binding.
 18. The non-transitorycomputer readable medium of claim 14 wherein said binding is anunmanaged binding.
 19. A non-transitory computer readable medium havinginstructions embodied therein that when executed cause a computer systemto perform a method for dynamically binding data in an application, saidmethod comprising: creating an expression via a framework based on inputfrom a developer; receiving said expression at an expression enginewherein said expression describes a relation between a first property ofa first data of said application to a first property of a second data ofsaid application, wherein said first data is associated with apresentation layer of said application and wherein said second data isassociated with a database layer of said application; querying saidfirst data and said second data for run time type information (RTTI) viasaid expression engine; creating a binding between said first data andsaid second data based on said relation and said RTTI via saidexpression engine; changing said first property of said second databased on a change to said first property of said first data wherein saidchanging occurs because of said binding; orchestrating the receiving theexpression, the creating the binding, and the changing the firstproperty via the framework to manage when the expression is executed inthe application; and moving said second data from said database layer ofsaid application to said presentation layer of said application based onsaid binding during an execution of said application.